Uplink grant selection for a wireless device and wireless network

ABSTRACT

A wireless device receives message(s) comprising configuration parameters for a cell. A first DCI is received in a first TTI and comprises: a first field indicating a first resource block assignment; and a first trigger field indicating whether the first DCI is a first triggered DCI. A second DCI is received in a second TTI and comprises: a second field indicating a second resource block assignment; and a second trigger field indicating whether the second DCI is a second triggered DCI. A third DCI is received in a third TTI via a common control channel of the cell and comprises a third trigger field indicating a trigger. The first DCI or the second DCI may be selected as a selected DCI at least based on a relative start time of the first TTI and the second TTI. Transport block(s) are transmitted employing the selected DCI in response to the trigger.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/399,932, filed Sep. 26, 2016, U.S. Provisional Application No.62/399,938, filed Sep. 26, 2016, U.S. Provisional Application No.62/399,941, filed Sep. 26, 2016, U.S. Provisional Application No.62/399,946, filed Sep. 26, 2016, U.S. Provisional Application No.62/399,947, filed Sep. 26, 2016, and U.S. Provisional Application No.62/405,885, filed Oct. 8, 2016 which are hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is an example diagram depicting OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 4 is an example block diagram of a base station and a wirelessdevice as per an aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10 is an example diagram depicting a downlink burst as per anaspect of an embodiment of the present disclosure.

FIG. 11 depicts examples of activation/deactivation MAC control elementas per an aspect of an embodiment of the present disclosure.

FIG. 12 is an example diagram depicting trigger A and trigger B in a2-stage triggered grant as per an aspect of an embodiment of the presentdisclosure.

FIG. 13 is an example diagram depicting multiple uplink grants anduplink transmissions as per an aspect of an embodiment of the presentdisclosure.

FIG. 14 is an example diagram depicting multiple uplink grants anduplink transmissions as per an aspect of an embodiment of the presentdisclosure.

FIG. 15 is an example diagram depicting multiple uplink grants anduplink transmissions as per an aspect of an embodiment of the presentdisclosure.

FIG. 16 is an example diagram depicting multiple uplink grants anduplink transmissions as per an aspect of an embodiment of the presentdisclosure.

FIG. 17 is an example diagram depicting multiple uplink grants anduplink transmissions as per an aspect of an embodiment of the presentdisclosure.

FIG. 18 is an example diagram depicting UE capability for uplinktransmissions as per an aspect of an embodiment of the presentdisclosure.

FIG. 19 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 20 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 21 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 22 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 23 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation ofcarrier aggregation. Embodiments of the technology disclosed herein maybe employed in the technical field of multicarrier communicationsystems.

The following Acronyms are used throughout the present disclosure:

-   ASIC application-specific integrated circuit-   BPSK binary phase shift keying-   CA carrier aggregation-   CSI channel state information-   CDMA code division multiple access-   CSS common search space-   CPLD complex programmable logic devices-   CC component carrier-   DL downlink-   CI downlink control information-   DC dual connectivity-   EPC evolved packet core-   E-UTRAN evolved-universal terrestrial radio access network-   FPGA field programmable gate arrays-   FDD frequency division multiplexing-   DL hardware description languages-   HARQ hybrid automatic repeat request-   IE information element-   LAA licensed assisted access-   LTE long term evolution-   CG master cell group-   MeNB master evolved node B-   MIB master information block-   MAC media access control-   AC media access control-   MME mobility management entity-   NAS non-access stratum-   OFDM orthogonal frequency division multiplexing-   PDCP packet data convergence protocol-   PDU packet data unit-   PHY physical-   PDCCH physical downlink control channel-   PHICH physical HARQ indicator channel-   PUCCH physical uplink control channel-   PUSCH physical uplink shared channel-   PCell primary cell-   PCell primary cell-   PCC primary component carrier-   PSCell primary secondary cell-   pTAG primary timing advance group-   QAM quadrature amplitude modulation-   QPSK quadrature phase shift keying-   RBG Resource Block Groups-   RLC radio link control-   RRC radio resource control-   RA random access-   RB resource blocks-   SCC secondary component carrier-   SCell secondary cell-   Scell secondary cells-   SCG secondary cell group-   SeNB secondary evolved node B-   sTAGs secondary timing advance group-   SDU service data unit-   S-GW serving gateway-   SRB signaling radio bearer-   SC-OFDM single carrier-OFDM-   SFN system frame number-   SIB system information block-   TAI tracking area identifier-   TAT time alignment timer-   TDD time division duplexing-   TDMA time division multiple access-   TA timing advance-   TAG timing advance group-   TB transport block-   UL uplink-   UE user equipment-   VHDL VHSIC hardware description language

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, the radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as 0.5 msec, 1 msec,2 msec, and 5 msec may also be supported. Subframe(s) may consist of twoor more slots (for example, slots 206 and 207). For the example of FDD,10 subframes may be available for downlink transmission and 10 subframesmay be available for uplink transmissions in each 10 ms interval. Uplinkand downlink transmissions may be separated in the frequency domain.Slot(s) may include a plurality of OFDM symbols 203. The number of OFDMsymbols 203 in a slot 206 may depend on the cyclic prefix length andsubcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs (in this example 6 to 100 RBs) may depend,at least in part, on the downlink transmission bandwidth 306 configuredin the cell. The smallest radio resource unit may be called a resourceelement (e.g. 301). Resource elements may be grouped into resourceblocks (e.g. 302). Resource blocks may be grouped into larger radioresources called Resource Block Groups (RBG) (e.g. 303). The transmittedsignal in slot 206 may be described by one or several resource grids ofa plurality of subcarriers and a plurality of OFDM symbols. Resourceblocks may be used to describe the mapping of certain physical channelsto resource elements. Other pre-defined groupings of physical resourceelements may be implemented in the system depending on the radiotechnology. For example, 24 subcarriers may be grouped as a radio blockfor a duration of 5 msec. In an illustrative example, a resource blockmay correspond to one slot in the time domain and 180 kHz in thefrequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to aspects of an embodiments, transceiver(s) may be employed.A transceiver is a device that includes both a transmitter and receiver.Transceivers may be employed in devices such as wireless devices, basestations, relay nodes, and/or the like. Example embodiments for radiotechnology implemented in communication interface 402, 407 and wirelesslink 411 are illustrated are FIG. 1, FIG. 2, FIG. 3, FIG. 5, andassociated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to various aspects of an embodiment, an LTE network mayinclude a multitude of base stations, providing a user planePDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towardsthe wireless device. The base station(s) may be interconnected withother base station(s) (for example, interconnected employing an X2interface). Base stations may also be connected employing, for example,an S1 interface to an EPC. For example, base stations may beinterconnected to the MME employing the S1-MME interface and to the S-G)employing the S1-U interface. The S1 interface may support amany-to-many relation between MMEs/Serving Gateways and base stations. Abase station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink,the carrier corresponding to the PCell may be the Uplink PrimaryComponent Carrier (UL PCC). Depending on wireless device capabilities,Secondary Cells (SCells) may be configured to form together with thePCell a set of serving cells. In the downlink, the carrier correspondingto an SCell may be a Downlink Secondary Component Carrier (DL SCC),while in the uplink, it may be an Uplink Secondary Component Carrier (ULSCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may apply,for example, to carrier activation. When the specification indicatesthat a first carrier is activated, the specification may also mean thatthe cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE release with agiven capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTEtechnology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand DC as per an aspect of an embodiment of the present disclosure.E-UTRAN may support Dual Connectivity (DC) operation whereby a multipleRX/TX UE in RRC_CONNECTED may be configured to utilize radio resourcesprovided by two schedulers located in two eNBs connected via a non-idealbackhaul over the X2 interface. eNBs involved in DC for a certain UE mayassume two different roles: an eNB may either act as an MeNB or as anSeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanismsimplemented in DC may be extended to cover more than two eNBs. FIG. 7illustrates one example structure for the UE side MAC entities when aMaster Cell Group (MCG) and a Secondary Cell Group (SCG) are configured,and it may not restrict implementation. Media Broadcast MulticastService (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses maydepend on how the bearer is setup. Three alternatives may exist, an MCGbearer, an SCG bearer and a split bearer as shown in FIG. 6. RRC may belocated in MeNB and SRBs may be configured as a MCG bearer type and mayuse the radio resources of the MeNB. DC may also be described as havingat least one bearer configured to use radio resources provided by theSeNB. DC may or may not be configured/implemented in example embodimentsof the disclosure.

In the case of DC, the UE may be configured with two MAC entities: oneMAC entity for MeNB, and one MAC entity for SeNB. In DC, the configuredset of serving cells for a UE may comprise two subsets: the Master CellGroup (MCG) containing the serving cells of the MeNB, and the SecondaryCell Group (SCG) containing the serving cells of the SeNB. For a SCG,one or more of the following may be applied. At least one cell in theSCG may have a configured UL CC and one of them, named PSCell (or PCellof SCG, or sometimes called PCell), may be configured with PUCCHresources. When the SCG is configured, there may be at least one SCGbearer or one Split bearer. Upon detection of a physical layer problemor a random access problem on a PSCell, or the maximum number of RLCretransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG may be stopped, anda MeNB may be informed by the UE of a SCG failure type. For splitbearer, the DL data transfer over the MeNB may be maintained. The RLC AMbearer may be configured for the split bearer. Like a PCell, a PSCellmay not be de-activated. A PSCell may be changed with a SCG change (forexample, with a security key change and a RACH procedure), and/orneither a direct bearer type change between a Split bearer and a SCGbearer nor simultaneous configuration of a SCG and a Split bearer may besupported.

With respect to the interaction between a MeNB and a SeNB, one or moreof the following principles may be applied. The MeNB may maintain theRRM measurement configuration of the UE and may, (for example, based onreceived measurement reports or traffic conditions or bearer types),decide to ask a SeNB to provide additional resources (serving cells) fora UE. Upon receiving a request from the MeNB, a SeNB may create acontainer that may result in the configuration of additional servingcells for the UE (or decide that it has no resource available to do so).For UE capability coordination, the MeNB may provide (part of) the ASconfiguration and the UE capabilities to the SeNB. The MeNB and the SeNBmay exchange information about a UE configuration by employing RRCcontainers (inter-node messages) carried in X2 messages. The SeNB mayinitiate a reconfiguration of its existing serving cells (for example, aPUCCH towards the SeNB). The SeNB may decide which cell is the PSCellwithin the SCG. The MeNB may not change the content of the RRCconfiguration provided by the SeNB. In the case of a SCG addition and aSCG SCell addition, the MeNB may provide the latest measurement resultsfor the SCG cell(s). Both a MeNB and a SeNB may know the SFN andsubframe offset of each other by OAM, (for example, for the purpose ofDRX alignment and identification of a measurement gap). In an example,when adding a new SCG SCell, dedicated RRC signaling may be used forsending required system information of the cell as for CA, except forthe SFN acquired from a MIB of the PSCell of a SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprises aPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell11, and an sTAG1 includes SCell2 andSCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported ina cell group (MCG or SCG) and other example TAG configurations may alsobe provided. In various examples in this disclosure, example mechanismsare described for a pTAG and an sTAG. Some of the example mechanisms maybe applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to an embodiment, initial timing alignment may be achievedthrough a random access procedure. This may involve a UE transmitting arandom access preamble and an eNB responding with an initial TA commandNTA (amount of timing advance) within a random access response window.The start of the random access preamble may be aligned with the start ofa corresponding uplink subframe at the UE assuming NTA=0. The eNB mayestimate the uplink timing from the random access preamble transmittedby the UE. The TA command may be derived by the eNB based on theestimation of the difference between the desired UL timing and theactual UL timing. The UE may determine the initial uplink transmissiontiming relative to the corresponding downlink of the sTAG on which thepreamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to variousaspects of an embodiment, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding(configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, (for example, at least one RRC reconfigurationmessage), may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of thepTAG. When an SCell is added/configured without a TAG index, the SCellmay be explicitly assigned to the pTAG. The PCell may not change its TAgroup and may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (for example, to establish, modify and/orrelease RBs, to perform handover, to setup, modify, and/or releasemeasurements, to add, modify, and/or release SCells). If the receivedRRC Connection Reconfiguration message includes the sCellToReleaseList,the UE may perform an SCell release. If the received RRC ConnectionReconfiguration message includes the sCellToAddModList, the UE mayperform SCell additions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH may only be transmitted onthe PCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. This mayrequire not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum may therefore needed for cellularoperators to meet the increasing demand. Considering user expectationsof high data rates along with seamless mobility, it may be beneficialthat more spectrum be made available for deploying macro cells as wellas small cells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, may be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA may offer an alternative for operators to make use ofunlicensed spectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAmay utilize at least energy detection to determine the presence orabsence of other signals on a channel in order to determine if a channelis occupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission. Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by UEs, time & frequency synchronizationof UEs, and/or the like.

In an example embodiment, a DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the eNBtransmissions can start only at the subframe boundary. LAA may supporttransmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

An LBT procedure may be employed for fair and friendly coexistence ofLAA with other operators and technologies operating in an unlicensedspectrum. LBT procedures on a node attempting to transmit on a carrierin an unlicensed spectrum may require the node to perform a clearchannel assessment to determine if the channel is free for use. An LBTprocedure may involve at least energy detection to determine if thechannel is being used. For example, regulatory requirements in someregions, for example, in Europe, may specify an energy detectionthreshold such that if a node receives energy greater than thisthreshold, the node assumes that the channel is not free. While nodesmay follow such regulatory requirements, a node may optionally use alower threshold for energy detection than that specified by regulatoryrequirements. In an example, LAA may employ a mechanism to adaptivelychange the energy detection threshold. For example, LAA may employ amechanism to adaptively lower the energy detection threshold from anupper bound. Adaptation mechanism(s) may not preclude static orsemi-static setting of the threshold. In an example a Category 4 LBTmechanism or other type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies, no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (for example, LBT withoutrandom back-off) may be implemented. The duration of time that thechannel is sensed to be idle before the transmitting entity transmitsmay be deterministic. In an example, Category 3 (for example, LBT withrandom back-off with a contention window of fixed size) may beimplemented. The LBT procedure may have the following procedure as oneof its components. The transmitting entity may draw a random number Nwithin a contention window. The size of the contention window may bespecified by the minimum and maximum value of N. The size of thecontention window may be fixed. The random number N may be employed inthe LBT procedure to determine the duration of time that the channel issensed to be idle before the transmitting entity transmits on thechannel. In an example, Category 4 (for example, LBT with randomback-off with a contention window of variable size) may be implemented.The transmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by a minimumand maximum value of N. The transmitting entity may vary the size of thecontention window when drawing the random number N. The random number Nmay be employed in the LBT procedure to determine the duration of timethat the channel is sensed to be idle before the transmitting entitytransmits on the channel.

LAA may employ uplink LBT at the UE. The UL LBT scheme may be differentfrom the DL LBT scheme (for example, by using different LBT mechanismsor parameters), since the LAA UL may be based on scheduled access whichaffects a UE's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme include, but are not limited to,multiplexing of multiple UEs in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. A UL transmission burst from aUE perspective may be a continuous transmission from a UE with notransmission immediately before or after from the same UE on the sameCC. In an example, a UL transmission burst may be defined from a UEperspective. In an example, a UL transmission burst may be defined froman eNB perspective. In an example, in case of an eNB operating DL+UL LAAover the same unlicensed carrier, DL transmission burst(s) and ULtransmission burst(s) on LAA may be scheduled in a TDM manner over thesame unlicensed carrier. For example, an instant in time may be part ofa DL transmission burst or an UL transmission burst.

In an example embodiment, in an unlicensed cell, a downlink burst may bestarted in a subframe. When an eNB accesses the channel, the eNB maytransmit for a duration of one or more subframes. The duration maydepend on a maximum configured burst duration in an eNB, the dataavailable for transmission, and/or eNB scheduling algorithm. FIG. 10shows an example downlink burst in an unlicensed (e.g. licensed assistedaccess) cell. The maximum configured burst duration in the exampleembodiment may be configured in the eNB. An eNB may transmit the maximumconfigured burst duration to a UE employing an RRC configurationmessage.

The wireless device may receive from a base station at least one message(for example, an RRC) comprising configuration parameters of a pluralityof cells. The plurality of cells may comprise at least one cell of afirst type (e.g. license cell) and at least one cell of a second type(e.g. unlicensed cell, an LAA cell). The configuration parameters of acell may, for example, comprise configuration parameters for physicalchannels, (for example, a ePDCCH, PDSCH, PUSCH, PUCCH and/or the like).The wireless device may determine transmission powers for one or moreuplink channels. The wireless device may transmit uplink signals via atleast one uplink channel based on the determined transmission powers.

In an example embodiments, LTE transmission time may include frames, anda frame may include many subframes. The size of various time domainfields in the time domain may be expressed as a number of time unitsT_(s)1/(15000<2048) seconds. Downlink, uplink and sidelink transmissionsmay be organized into radio frames with T_(f)=307200<T_(s)=10 msduration. In an example LTE implementation, at least three radio framestructures may be supported: Type 1, applicable to FDD, Type 2,applicable to TDD, Type 3, applicable to LAA secondary cell operation.LAA secondary cell operation applies to frame structure type 3.

Transmissions in multiple cells may be aggregated where one or moresecondary cells may be used in addition to the primary cell. In case ofmulti-cell aggregation, different frame structures may be used in thedifferent serving cells.

Frame structure type 1 may be applicable to both full duplex and halfduplex FDD. A radio frame is T_(f)=307200 T_(s)=10 ms long radio frameis long and may comprise 20 slots of length T_(slot)=15360 T_(s)=0.5 ms,numbered from 0 to 19. A subframe may include two consecutive slotswhere subframe i comprises of slots 2i and 2i+1.

For FDD, 10 subframes are available for downlink transmission and 10subframes are available for uplink transmissions in a 10 ms interval.Uplink and downlink transmissions are separated in the frequency domain.In half-duplex FDD operation, the UE may not transmit and receive at thesame time while there may not be such restrictions in full-duplex FDD.

Frame structure type 2 may be applicable to TDD. A radio frame of lengthT_(f)=307200 T_(s)=10 ms may comprise of two half-frames of length153600 T_(s)=5 ms. A half-frame may comprise five subframes of length30720 T_(s)=1 ms. A subframe i may comprise two slots, 2i and 2i+1, oflength T_(slot)=15360 T_(s)=0.5 ms.

The uplink-downlink configuration in a cell may vary between frames andcontrols in which subframes uplink or downlink transmissions may takeplace in the current frame. The uplink-downlink configuration in thecurrent frame is obtained via control signaling.

An example subframe in a radio frame, “may be a downlink subframereserved for downlink transmissions, may be an uplink subframe reservedfor uplink transmissions or may be a special subframe with the threefields DwPTS, GP and UpPTS. The length of DwPTS and UpPTS are subject tothe total length of DwPTS, GP and UpPTS being equal to 30720 T_(s)=1 ms.

Uplink-downlink configurations with both 5 ms and 10 msdownlink-to-uplink switch-point periodicity may be supported. In case of5 ms downlink-to-uplink switch-point periodicity, the special subframemay exist in both half-frames. In case of 10 ms downlink-to-uplinkswitch-point periodicity, the special subframe may exist in the firsthalf-frame.

Subframes 0 and 5 and DwPTS may be reserved for downlink transmission.UpPTS and the subframe immediately following the special subframe may bereserved for uplink transmission.

In an example, in case multiple cells are aggregated, the UE may assumethat the guard period of the special subframe in the cells using framestructure Type 2 have an overlap of at least 1456. T_(s).

In an example, in case multiple cells with different uplink-downlinkconfigurations in the current radio frame are aggregated and the UE isnot capable of simultaneous reception and transmission in the aggregatedcells, the following constraints may apply. if the subframe in theprimary cell is a downlink subframe, the UE may not transmit any signalor channel on a secondary cell in the same subframe. If the subframe inthe primary cell is an uplink subframe, the UE may not be expected toreceive any downlink transmissions on a secondary cell in the samesubframe. If the subframe in the primary cell is a special subframe andthe same subframe in a secondary cell is a downlink subframe, the UE maynot be expected to receive PDSCH/EPDCCH/PMCH/PRS transmissions in thesecondary cell in the same subframe, and the UE may not be expected toreceive any other signals on the secondary cell in OFDM symbols thatoverlaps with the guard period or UpPTS in the primary cell.

Frame structure type 3 may be applicable to LAA secondary cell operationwith normal cyclic prefix. A radio frame is T_(f)=307200 T_(x)=10 mslong and comprises of 20 slots of length T_(slot)=15360 T_(s)=0.5 ms,numbered from 0 to 19. A subframe may comprise as two consecutive slotswhere subframe i comprises slots 2i and 2i+1.

The 10 subframes within a radio frame are available for downlinktransmissions. Downlink transmissions occupy one or more consecutivesubframes, starting anywhere within a subframe and ending with the lastsubframe either fully occupied or following one of the DwPTS durations.Subframes may be available for uplink transmission when LAA uplink issupported.

FIG. 12 shows an example 2-stage triggered grant with trigger A andtrigger B. In an example embodiment, DCI 0A/4A/0B/4B may include a bitto indicate whether an UL grant is a triggered grant or not. If it is atriggered grant, the UE may transmit after receiving a trigger (e.g. onebit set to 1) in the PDCCH DCI scrambled with CC-RNTI in a subframereceived after the subframe carrying the trigger. The timing between the2nd trigger transmitted in subframe N and an earliest UL transmissionmay be a UE capability, if the earliest UL transmission is beforesubframe N+4 (e.g. UE capability signaling between transmission insubframe N+1 and N+2 and N+3). DCI 0A/4A/0B/4B may comprise one or morefields indicating resource block assignment, modulation and codingscheme, RV, HARQ information, transmit power control command, trigger A,and/or other physical layer parameters. The trigger may be receivedduring a validation duration. The validation duration may be determinedbased on a field in the DCI including the uplink grant. The UE maymonitor CC-RNTI for a trigger during the validation duration at leastuntil the trigger is received.

DCI format 1C is used for example for LAA common information. The DCIformat 1C in an LAA cell may comprise subframe configuration for an LAAcell—j bits (e.g., j=4) indicating a number of symbols. DCI format 1Cmay further comprise other information. DCI format 1C may furthercomprise, for example, k-bits (e.g. k=5) to indicate combinations ofoffset and burst duration. In an example, a code points may include{offset, duration} combinations as follows: combinations of {{1, 2, 3,4, 6}, {1, 2, 3, 4, 5, 6}}, Reserved, no signalling of burst and offset.The format of the bits may be defined according to a pre-defined table.DCI format 1C may further comprise PUSCH trigger field (e.g. 1 bit) toindicate a trigger for a two-stage grant. For example, value 1 mayindicate a trigger B and value 0 may indicate no trigger B. Reservedinformation bits may be added until the size is equal to that of format1C used for very compact scheduling of one PDSCH code-word.

In an example, if a serving cell is an LAA Scell, the UE may receivePDCCH with DCI CRC scrambled by CC-RNTI on the LAA SCell. In an example,the DCI CRC scrambled by CC-RNTI may be transmitted in the common searchspace of an LAA cell. Example PDCCH procedures are described here.

In an example, a control region of a serving cell may comprise of a setof CCEs, numbered from 0 to N_(CCE,k)−1 according, where N_(CCE,k) maybe the total number of CCEs in the control region of subframe k . The UEmay monitor a set of PDCCH candidates on one or more activated servingcells as configured by higher layer signalling for control information,where monitoring implies attempting to decode the PDCCHs in the setaccording to monitored DCI formats. A BL/CE UE may not be required tomonitor PDCCH.

In an example, the set of PDCCH candidates to monitor are defined interms of search spaces, where a search space S_(k) ^((L)) at aggregationlevel L∈{1, 2, 4, 8} is defined by a set of PDCCH candidates. For aserving cell on which PDCCH is monitored, the CCEs corresponding toPDCCH candidate m of the search space S_(k) ^((L)) are given byL{(Y_(k)+m′) mod └N_(CCE,k)/L┘}+i, where Y_(k) is defined below, i=0, .. . , L−1. For the common search space m′=m. For the PDCCH UE specificsearch space, for the serving cell on which PDCCH is monitored, if themonitoring UE is configured with carrier indicator field thenm′=m+M^((L)).n_(C1) where c_(C1) is the carrier indicator field value,else if the monitoring UE is not configured with carrier indicator fieldthen m′=m, where m=0, . . . , M^((L))−1M^((L)) is the number of PDCCHcandidates to monitor in the given search space.

In an example, if a UE is configured with higher layer parametercif-InSchedulingCell, the carrier indicator field value corresponds tocif-InSchedulingCell, otherwise, the carrier indicator field value isthe same as ServCellIndex. The UE may monitor one common search space ina non-DRX subframe at aggregation levels 4 and 8 on the primary cell. AUE may monitor common search space on a cell to decode the PDCCHsnecessary to receive MBMS on that cell when configured by higher layers.

In an example, if a UE is not configured for EPDCCH monitoring, and ifthe UE is not configured with a carrier indicator field, then the UE maymonitor one PDCCH UE-specific search space at aggregation levels 1, 2,4, 8 on an activated serving cell in every non-DRX subframe. If a UE isnot configured for EPDCCH monitoring, and if the UE is configured with acarrier indicator field, then the UE may monitor one or more UE-specificsearch spaces at aggregation levels 1, 2, 4, 8 on one or more activatedserving cells as configured by higher layer signalling in every non-DRXsubframe.

In an example, if a UE is configured for EPDCCH monitoring on a servingcell, and if that serving cell is activated, and if the UE is notconfigured with a carrier indicator field, then the UE may monitor onePDCCH UE-specific search space at aggregation levels 1, 2, 4, 8 on thatserving cell in non-DRX subframes where EPDCCH is not monitored on thatserving cell. If a UE is configured for EPDCCH monitoring on a servingcell, and if that serving cell is activated, and if the UE is configuredwith a carrier indicator field, then the UE may monitor one or morePDCCH UE-specific search spaces at aggregation levels 1, 2, 4, 8 on thatserving cell as configured by higher layer signalling in non-DRXsubframes where EPDCCH is not monitored on that serving cell. The commonand PDCCH UE-specific search spaces on the primary cell may overlap.

In an example, a UE configured with a carrier indicator field associatedwith monitoring PDCCH on serving cell c may monitor PDCCH configuredwith carrier indicator field and with CRC scrambled by C-RNTI in thePDCCH UE specific search space of serving cell c. A UE configured withthe carrier indicator field associated with monitoring PDCCH on theprimary cell may monitor PDCCH configured with carrier indicator fieldand with CRC scrambled by SPS C-RNTI in the PDCCH UE specific searchspace of the primary cell. The UE may monitor the common search spacefor PDCCH without carrier indicator field.

In an example, for the serving cell on which PDCCH is monitored, if theUE is not configured with a carrier indicator field, it may monitor thePDCCH UE specific search space for PDCCH without carrier indicatorfield, if the UE is configured with a carrier indicator field it maymonitor the PDCCH UE specific search space for PDCCH with carrierindicator field. If the UE is not configured with a LAA Scell, the UE isnot expected to monitor the PDCCH of a secondary cell if it isconfigured to monitor PDCCH with carrier indicator field correspondingto that secondary cell in another serving cell.

In an example, if the UE is configured with a LAA Scell, the UE is notexpected to monitor the PDCCH UE specific space of the LAA SCell if itis configured to monitor PDCCH with carrier indicator fieldcorresponding to that LAA Scell in another serving cell, where the UE isnot expected to be configured to monitor PDCCH with carrier indicatorfield in an LAA Scell; and where the UE is not expected to be scheduledwith PDSCH starting in the second slot in a subframe in an LAA Scell ifthe UE is configured to monitor PDCCH with carrier indicator fieldcorresponding to that LAA Scell in another serving cell.

In an example, for the serving cell on which PDCCH is monitored, the UEmay monitor PDCCH candidates at least for the same serving cell. A UEconfigured to monitor PDCCH candidates with CRC scrambled by C-RNTI orSPS C-RNTI with a common payload size and with the same first CCE indexn_(CCE) but with different sets of DCI information fields in the commonsearch space and/or PDCCH UE specific search space.

In an example, a UE configured to monitor PDCCH candidates in a givenserving cell with a given DCI format size with CIF, and CRC scrambled byC- RNTI, where the PDCCH candidates may have one or more possible valuesof CIF for the given DCI format size, may assume that a PDCCH candidatewith the given DCI format size may be transmitted in the given servingcell in any PDCCH UE specific search space corresponding to any of thepossible values of CIF for the given DCI format size.

In an example, if a serving cell is an LAA Scell, the UE may receivePDCCH with DCI CRC scrambled by CC-RNTI on the LAA Scell. The DCIformats that the UE may monitor depend on the configured transmissionmode of a serving cell.

Example subframe configuration for Frame Structure Type 3 are describedhere. If a UE detects PDCCH with DCI CRC scrambled by CC-RNTI insubframe n-1 or subframe n of a LAA Scell, the UE may assume theconfiguration of occupied OFDM symbols in subframe n of the LAA Scellaccording to the Subframe configuration for LAA field in the detectedDCI in subframe n-1 or subframe n.

In an example, the Subframe configuration for LAA field indicates theconfiguration of occupied OFDM symbols (e.g., OFDM symbols used fortransmission of downlink physical channels and/or physical signals) incurrent and/or next subframe according to a predefined table. If theconfiguration of occupied OFDM symbols for subframe n is indicated bythe Subframe configuration for LAA field in both subframe n-1 andsubframe n, the UE may assume that the same configuration of occupiedOFDM symbols is indicated in both subframe n-1 and subframe n.

In an example, if a UE detects PDCCH with DCI CRC scrambled by CC-RNTIin subframe n, and the UE does not detect PDCCH with DCI CRC scrambledby CC-RNTI in subframe n-1, and if the number of occupied OFDM symbolsfor subframe n indicated by the Subframe configuration for LAA field insubframe n is less than 14, the UE is not required to receive any otherphysical channels in subframe n.

In an example, if a UE does not detect PDCCH with DCI CRC scrambled byCC-RNTI containing Subframe Configuration for LAA field set to otherthan ‘1110’ and ‘1111’ in subframe n and the UE does not detect PDCCHwith DCI CRC scrambled by CC-RNTI containing Subframe Configuration forLAA field set to other than ‘1110’ and ‘1111’ in subframe n-1, the UE isnot required to use subframe n for updating CSI measurement.

In an example, the UE may detect PDCCH with DCI CRC scrambled by CC-RNTIby monitoring the following PDCCH candidates according to DCI Format 1C:one PDCCH candidate at aggregation level L=4 with the CCEs correspondingto the PDCCH candidate given by CCEs numbered 0, 1, 2, 3; one PDCCHcandidate at aggregation level L=8 with the CCEs corresponding to thePDCCH candidate given by CCEs numbered 0, 1, 2, 3, 4, 5, 6, 7.

In an example, if a serving cell is an LAA Scell, and if the higherlayer parameter subframeStartPosition for the Scell indicates ‘s07’, andif the UE detects PDCCH/EPDCCH intended for the UE starting in thesecond slot of a subframe, the UE may assume that OFDM symbols in thefirst slot of the subframe are not occupied, and OFDM symbols in thesecond slot of the subframe are occupied. If subframe n is a subframe inwhich OFDM symbols in the first slot are not occupied, the UE may assumethat the OFDM symbols are occupied in subframe n+1.

In an example embodiment, a field in DCI format 0A/4A/0B/4B for thetriggered grant, e.g. 4-bit SF timing, may be reused to signal to the UEa subframe for transmission after reception of the trigger. When a UEreceives a trigger in subframe N, the UE may be allowed to starttransmission in subframe N+X+Y. 2 bits are reused to indicate X. X={0,1, 2, 3} may be indicated to the UE reusing two bits in the DCI. Y maybe given by the UL burst offset in the C-PDCCH DCI scrambled by CC-RNTI(e.g. in the same subframe where the trigger is transmitted). The UE mayreceive signalling in the first DCI 0A/4A/0B/4B grant indicating thenumber of subframes after which the grant becomes invalid. The initialgrant may become invalid if M ms after the initial grant, no validtrigger has been received, e.g. M={8, 12, 16, 20}. In an example, a UEmay follow the LBT type indicated by the UL grant.

In an example embodiment, C(common)-PDCCH may indicate a pair of values(UL burst duration, offset). UL burst duration may be a number ofconsecutive UL subframes belonging to the same channel occupancy. Offsetmay be the number of subframes to the start of indicated UL burst fromthe start of the subframe carrying the C-PDCCH.

In an example embodiment, an LBT procedure may be switched to an LBTbased on 25 us CCA for any UL subframe from the subframe in whichC-PDCCH was received up to and including subframes until the end of thesignalled UL burst duration, for which the eNB had already indicated toperform Category 4 LBT. In an example, a UE may not switch to 25 us CCAif part of a set of contiguously scheduled subframes without gap appearsin the UL burst indication. The UE may not be required to receive any DLsignals/channels in a subframe indicated to be a UL subframe on thecarrier. In an example, 5 bits may be employed to indicate combinationsof offset and burst duration. Example code points include {offset,duration} combinations as follows: combinations of {{1, 2, 3, 4, 6}, {1,2, 3, 4, 5, 6}}, Reserved, no signalling of burst and offset. The formatof the bits may be defined according to a pre-defined table.

In an example embodiment, resource block assignment field in DCI0A/4A/0B/4B may be 6 bits. In an example, the 64 code points indicatedby the 6 bits may include the legacy RIV for contiguous interlaceallocation except the code points for the allocation of 7 contiguousinterlaces (70 PRBs). This set of code points may include 51 values.Additional code points may be defined for allocation of interlaces asfollows: 0, 1, 5, 6; 2, 3, 4, 7, 8, 9; 0, 5; 1, 6; 2, 7; 3, 8; 4, 9; 1,2, 3, 4, 6, 7, 8, 9. Remaining code points may be reserved.

In an example, the Activation/Deactivation MAC control element of oneoctet may be identified by a MAC PDU subheader with LCID 11000. FIG. 11shows example Activation/Deactivation MAC control elements. TheActivation/Deactivation MAC control element may have a fixed size andmay comprise of a single octet containing seven C-fields and oneR-field. Example Activation/Deactivation MAC control element with oneoctet is shown in FIG. 11. The Activation/Deactivation MAC controlelement may have a fixed size and may comprise of four octets containing31 C-fields and one R-field. Example Activation/Deactivation MAC controlelement of four octets is shown in FIG. 11. In an example, for the casewith no serving cell with a serving cell index (ServCellIndex) largerthan 7, Activation/Deactivation MAC control element of one octet may beapplied, otherwise Activation/Deactivation MAC control element of fouroctets may be applied. The fields in an Activation/Deactivation MACcontrol element may be interpreted as follows. Ci: if there is an SCellconfigured with SCellIndex i, this field may indicate theactivation/deactivation status of the SCell with SCellIndex i, else theMAC entity may ignore the Ci field. The Ci field may be set to “1” toindicate that the SCell with SCellIndex i is activated. The Ci field isset to “0” to indicate that the SCell with SCellIndex i is deactivated.R: Reserved bit, set to “0”.

In an example, if the MAC entity is configured with one or more SCells,the network may activate and deactivate the configured SCells. TheSpCell may remain activated. The network may activate and deactivate theSCell(s) by sending the Activation/Deactivation MAC control element. Inexample, the MAC entity may maintain a sCellDeactivationTimer timer fora configured SCell. sCellDeactivationTimer may be disabled for the SCellconfigured with PUCCH, if any. In example, the MAC entity may deactivatethe associated SCell upon its expiry. In an example, the same initialtimer value may apply to each instance of the sCellDeactivationTimer andit is configured by RRC. The configured SCells may be initiallydeactivated upon addition and after a handover. The configured SCGSCells are initially deactivated after a SCG change.

The MAC entity may for each TTI and for a configured SCell perform thefollowing: if the MAC entity receives an Activation/Deactivation MACcontrol element in this TTI activating the SCell, the MAC entity may inthe TTI according to a predefined timing, activate the SCell. A UE mayoperate the following for an activated SCell including: SRStransmissions on the SCell; CQI/PMI/RI/PTI/CRI reporting for the SCell;PDCCH monitoring on the SCell; PDCCH monitoring for the SCell; PUCCHtransmissions on the SCell, if configured.

If the MAC entity receives an Activation/Deactivation MAC controlelement in this TTI activating the SCell, the UE may start or restartthe sCellDeactivationTimer associated with the SCell and may triggerPHR. If the MAC entity receives an Activation/Deactivation MAC controlelement in this TTI deactivating the SCell or if thesCellDeactivationTimer associated with the activated SCell expires inthis TTI, in the TTI according to a predefined timing, the UE maydeactivate the SCell; stop the sCellDeactivationTimer associated withthe SCell; flush HARQ buffers associated with the SCell.

In an example embodiment, if the SCell is deactivated: the UE may nottransmit SRS on the SCell; not report CQI/PMI/RI/PTI/CRI for the SCell;not transmit on UL-SCH on the SCell; not transmit on RACH on the SCell;not monitor the PDCCH on the SCell; not monitor the PDCCH for the Cell;and/or not transmit PUCCH on the SCell. When SCell is deactivated, theongoing random access procedure on the SCell, if any, is aborted.

In an example embodiment, the sCellDeactivationTimer for a cell may bedisabled and there may be no need to manage sCellDeactivationTimer forthe cell and the cell may be activated or deactivated employing A/D MACCE.

In an example, when a single stage grant is configured, if PDCCH on theactivated SCell indicates an uplink grant or downlink assignment; or ifPDCCH on the Serving Cell scheduling the activated SCell indicates anuplink grant or a downlink assignment for the activated SCell: theUE/eNB may restart the sCellDeactivationTimer associated with the SCell.

In an example embodiment, an eNB may transmit one or more RRC messagescomprising one or more parameters (IEs). The one or more parameters maycomprise configuration parameters of one or more licensed cells and oneor more unlicensed cells (e.g. LAA cells). The one or more parametersmay comprise a sCellDeactivationTimer value.

For example, sCellDeactivationTimer ENUMERATED {rf2,rf4, rf8, rf16,rf32, rf64, rf128, spare} OPTIONAL. SCell deactivation timer value maybe in number of radio frames. For example, value rf4 corresponds to 4radio frames, value rf8 corresponds to 8 radio frames and so on. In anexample, E-UTRAN may configure the field if the UE is configured withone or more SCells other than the PSCell and PUCCH SCell. If the fieldis absent, the UE may delete any existing value for this field andassume the value to be set to infinity. In an example, the same valuemay apply for each SCell of a Cell Group (e.g. MCG or SCG) (theassociated functionality is performed independently for each SCell).Field sCellDeactivationTimer may not apply to an SCell, when the for thesCellDeactivationTimer is disabled for the SCell (e.g. PUCCH SCelland/or other SCells).

A UE may Support UL/DL Scheduling Combinations: Self-scheduling on DLand cross-carrier scheduling on UL. The UE to monitor for DCI formatsscheduling PUSCH of a single eLAA Scell on one UL licensed-bandscheduling cell, e.g. DCI formats 0A/0B, Formats 4A/4B (e.g. ifconfigured for TM2). The UE may monitor for DCI formats scheduling LAAPDSCH on the LAA SCell, e.g. DCI formats 1A/1B/1D/1/2A/2/2B/2C/2D. Inlegacy RRC mechanisms, when cross carrier scheduling is configured byRRC for an SCell, the scheduling cell schedules both downlink and uplink(if configured) grants for the scheduled cell. In an example, the RRCsignaling and cross carrier scheduling may be enhanced. RRC signalingmay configure self-scheduling for DL and cross-carrier scheduling forUL, for example for an LAA cell. For example, a new parameter in thecross-carrier scheduling configuration parameters may indicate whetherthe cross-carrier scheduling is for both downlink scheduling and uplinkscheduling or is for uplink scheduling (and DL is self-scheduled). In anexample, a licensed cell may be configured for cross-carrier schedulingan unlicensed (e.g. LAA) cell.

The IE CrossCarrierSchedulingConfig may used to specify theconfiguration when the cross carrier scheduling is used in a cell. In anexample, the IE CrossCarrierScheduling Config may comprise cif-Presence,schedulingCellId, and pdsch-Start. In an example, the IECrossCarrierSchedulingConfig may comprise cif-Presence,schedulingCellId, pdsch-Start, and cif-InSchedulingCell. In an example,cif-Presence may be used to indicate whether carrier indicator field ispresent (value true) or not (value false) in PDCCH/EPDCCH DCI formats.In an example, pdsch-Start field may indicate the starting OFDM symbolof PDSCH for the concerned SCell. In an example, values 1, 2, 3 areapplicable when d1-Bandwidth for the concerned SCell is greater than 10resource blocks, values 2, 3, 4 are applicable when d1-Bandwidth for theconcerned SCell is less than or equal to 10 resource blocks. In anexample, cif-InSchedulingCell field may indicate the CIF value used inthe scheduling cell to indicate this cell. In an example,schedulingCellId field may indicates which cell signals the downlinkallocations and/or uplink grants, if applicable, for the concernedSCell. In case the UE is configured with DC, the scheduling cell is partof the same cell group (e.g. MCG or SCG) as the scheduled. In anexample, an IE in IE CrossCarrierSchedulingConfig of an RRC message mayindicate self-scheduling on DL and cross-carrier scheduling on UL (forexample for an LAA cell). In an example, an IE in IECrossCarrierSchedulingConfig of an RRC message may indicatecross-carrier scheduling on both downlink and uplink.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.The plurality of cells may comprise a first cell. In an example, thefirst cell may be an LAA cell. The wireless device may receive a DCI foruplink transmission on the first cell. In an example, the DCI format maybe one of formats 0A/4A/0B/4B. The DCI may comprise a field indicatingwhether the UL grant for the first cell is a triggered grant or nottriggered. In an example, the field may comprise a single bit. In anexample, if the UL grant is a triggered grant, the UE may transmit afterreceiving a trigger (e.g., a one-bit trigger) in a PDCCH DCI (e.g., withCRC scrambled by CC-RNTI) in a subframe received after the subframecarrying the UL grant. The timing between the second trigger transmittedin subframe N and the earliest UL transmission may be a UE capability,if the earliest UL transmission is before subframe N+4 (e.g., subframeN+1 or N+2 or N+3).

In an example, DCI format 0A/4A/0B/4B may comprise a SF timing fieldthat may be used to indicate a transmission timing offset. In anexample, the SF timing field may comprise four bits. The DCI format0A/4A/0B/4B may indicate a one-stage grant or a two-stage (e.g.,triggered) grant. In an example, the four-bit SF timing field in DCIformat 0A/4A/0B/4B may be reused for the triggered/two-stage grant. Inan example, two bits out of the four bits in the SF timing field may bereused to indicate a value X. In an example, having received a triggerin subframe N, the UE may be allowed to start transmission in subframeN+X+Y where X is indicated reusing two bits in the DCI and may take oneof the four values {0, 1, 2, 3}. In an example, Y may be given by an ULburst offset field in the C-PDCCH DCI (e.g., scrambled by CC-RNTI) inthe same subframe where the trigger is transmitted. The C-PDCCH DCI maybe received in a common control channel of the first cell.

In an example, for a two-stage grant scheduling the first cell, the UEmay receive a two-bit signaling in the first DCI 0A/4A/0B/4B grant(e.g., two bits out of the four bits SF timing field) indicating anumber of subframes after which the grant becomes invalid in response tonot receiving a trigger in common DCI. In an example, the first DCI maybecome invalid if no valid trigger is received M subframes after thefirst grant. The two-bit signaling in the DCI may indicate one of thefours possible values for M, e.g., {8, 12, 16, 20}. In an exampleembodiment, a UE may receive two or more triggers on common PDCCH withinthe M ms time window (and after which the grant is invalidated) duringwhich a trigger may be received. In an example, the UE may consider thefirst received trigger to determine the transmission timing for thegrant. In an example, the UE may stop monitoring common control channelfor CC-RNTI after receiving the first trigger. In an example embodiment,a UE may receive a single trigger for two or more two-stage grants. TheUE may consider the trigger to determine the transmission timing for thetwo or more grants.

In example embodiments, a grant (e.g., single-stage or two-stage) mayschedule an LAA cell with cross-carrier scheduling (e.g., on ascheduling carrier other than the LAA cell) or self-carrier scheduling(e.g., on the LAA cell).

In an example, a time duration between a first TTI where the grant isreceived, and a second TTI where a transmission occurs may depend on aDCI offset field and/or an offset field in a common control channeland/or a timing of a trigger for a two-stage grant. A UE may receivemultiple grants that schedule transmission and assign resource blocks inthe same TTI. Transmission of multiple TBs corresponding to multiplegrants in the same TTI may increase complexity in the UE and/or mayincrease the peak to average ratio in the UE transceiver. There is aneed for implementation of enhanced processes wherein a UE can handlemultiple grants pointing to a transmission in the same TTI. Exampleembodiments enhances UE transmission mechanisms to enable receivingmultiple grants in multiple TTIs that result in transmission in the sameTTI. Example embodiments also enable an eNB to transmit new grantspointing to transmission in the same TTI as another grant.

In an example, a UE may receive one or more single-stage and/ortwo-stage uplink grants that schedule a first cell (e.g., an LAA cell).An uplink grant may use one of the DCI formats 0A/4A/0B/4B. A two-stageuplink grant may comprise an UL grant transmitting the schedulinginformation and a trigger in the PDCCH DCI scrambled with CC-RNTI in asubframe received after the subframe carrying the UL grant. Two or moreof the grants (single-stage and/or two-stage) may point to and allocateresources of the LAA cell on the same subframe. In such scenario, a UEmay consider one of the grants and may ignore the other grant(s).

Example scenarios where a plurality of grants (e.g., single-stage and/ortwo-stage grants) allocate resources in the same subframe are shown inFIG. 13, FIG. 14, FIG. 15, FIG. 16 and FIG. 17. The example scenariosshow different examples of arrival times of two-stage grant DCI, triggerand one-stage grant DCI. For example, FIG. 16 shows an example that twotwo-stage grants are triggered by a trigger. The two two-stage grantspoint to and schedule resources for the same subframe. For example, FIG.17 shows an example of two one-stage grants that schedule the samesubframe.

In an example embodiment, the UE may consider the information in thelatest received grant to create and attempt to transmit transportblock(s) on the scheduled subframe. In an example, if one or more of thegrants scheduling the UE on the subframe is (are) two-stage, the UE mayconsider the subframe that the DCI for a two-stage grant is received forcomparing the arrival times of the grants and/or determining the grantto use for creating the TB(s) to be transmitted on the subframe. In anexample, the UE may use the scheduling information in UL grantconsidered for the subframe (e.g., resource assignment, HARQ processnumber and redundancy version, MCS, Cyclic shift for DM RS and OCCindex, etc.) to create and attempt to transmit the transport block(s).In an example, the considered uplink grant may be multi-subframe grantand the UE may create and attempt to transmit multiple consecutivetransport blocks. In an example in FIG. 13, the wireless device receivesthe one-stage grant DCI later than the two-stage grant DCI. The wirelessdevice may use the information in the one-stage grant DCI to create andtransmit the TB(s). In an example in FIG. 14, the wireless devicereceives the one-stage grant DCI later than the two-stage grant DCI. Thewireless device may use the information in the one-stage grant DCI tocreate and transmit the TB(s). In an example in FIG. 15, the wirelessdevice receives the two-stage grant later than the one-stage grant. Thewireless device may use the information in the two-stage grant DCI tocreate and transmit the TB(s). In an example in FIG. 16, the wirelessdevice receives two two-stage grants. The wireless device may use theinformation in the second (e.g., later received) two-stage grant tocreate and transmit the TB(s). In an example in FIG. 17, the wirelessdevice may receive two one-stage grants. The wireless device may use theinformation in the second (e.g., later received) one-stage grant tocreate and transmit the TB(s).

In an example embodiment, the UE may consider the information in thelatest received grant to create and attempt to transmit transportblock(s) on the scheduled subframe. In an example, if one or more of thegrants scheduling the UE on the subframe is (are) two-stage, the UE mayconsider the subframe that the trigger for a two-stage grant is receivedfor comparing the arrival times of the grants and/or determining thegrant to use for creating the TB(s) to be transmitted on the subframe.In an example, if a single trigger triggers two or more two-stage grantsscheduling the same subframe and the trigger arrives later than othertriggers or grants scheduling the same subframe, the UE may consider theinformation in the two-stage grant triggered by the trigger that arrivesthe latest to transmit a transport block in the scheduled subframe. Inan example, the UE may use the scheduling information in UL grantconsidered for the subframe (e.g., resource assignment, HARQ processnumber and redundancy version, MCS, Cyclic shift for DM RS and OCCindex, etc.) to create and attempt to transmit the transport block(s).In an example, the considered uplink grant may be multi-subframe grantand the UE may create and attempt to transmit multiple consecutivetransport blocks. In an example in FIG. 13, the wireless device receivesthe trigger for a two-stage grant DCI later than a one-stage grant DCI.The wireless device may use the information in the two-stage grant DCIto create and transmit the TB(s). In an example in FIG. 14, the wirelessdevice receives the one-stage grant DCI later than the trigger for thetwo-stage grant. The wireless device may use the information in theone-stage grant DCI to create and transmit the TB(s). In an example inFIG. 15, the wireless device receives the trigger for the two-stagegrant later than the one-stage grant. The wireless device may use theinformation in the two-stage grant DCI to create and transmit the TB(s).In an example in FIG. 16, the wireless device receives two two-stagegrants and a single trigger. The wireless device may use the informationin the second (e.g., later received) two-stage grant to create andtransmit the TB(s). In an example in FIG. 17, the wireless device mayreceive two one-stage grants. The wireless device may use theinformation in the second (e.g., later received) one-stage grant tocreate and transmit the TB(s).

In an example embodiment, the UE may consider the information in thefirst received grant to create and attempt to transmit transportblock(s) on the scheduled subframe. In an example, if one or more of thegrants scheduling the UE on the subframe is (are) two-stage, the UE mayconsider the subframe that the DCI for a two-stage grant is received forcomparing the arrival times of the grants and/or determining the grantto use for creating the TB(s) to be transmitted on the subframe. In anexample, the UE may use the scheduling information in UL grantconsidered for the subframe (e.g., resource assignment, HARQ processnumber and redundancy version, MCS, Cyclic shift for DM RS and OCCindex, etc.) to create and attempt to transmit the transport block(s).In an example, the considered uplink grant may be multi-subframe grantand the UE may create and attempt to transmit multiple consecutivetransport blocks. In an example in FIG. 13, the wireless device receivesa two-stage grant DCI earlier than a one-stage grant DCI. The wirelessdevice may use the information in the two-stage grant DCI to create andtransmit the TB(s). In an example in FIG. 14, the wireless devicereceives the two-stage grant DCI earlier than the one-stage grant. Thewireless device may use the information in the two-stage grant DCI tocreate and transmit the TB(s). In an example in FIG. 15, the wirelessdevice receives the one-stage grant earlier than the two-stage grant.The wireless device may use the information in the one-stage grant DCIto create and transmit the TB(s). In an example in FIG. 16, the wirelessdevice receives two two-stage grants and a single trigger. The wirelessdevice may use the information in the first (e.g., earlier received)two-stage grant to create and transmit the TB(s). In an example in FIG.17, the wireless device may receive two one-stage grants. The wirelessdevice may use the information in the first (e.g., earlier received)one-stage grant to create and transmit the TB(s).

In an example embodiment, the UE may consider the information in thefirst received grant to create and attempt to transmit transportblock(s) on the scheduled subframe. In an example, if one or more of thegrants scheduling the UE on the subframe is (are) two-stage, the UE mayconsider the subframe that the trigger for a two-stage grant is receivedfor comparing the arrival times of the grants and/or determining thegrant to use for creating the TB(s) to be transmitted on the subframe.In an example, if a single trigger triggers two or more two-stage grantsscheduling the same subframe and the trigger arrives sooner than othertriggers or grants scheduling the same subframe (except for thetwo-stage grants that the trigger triggers), the UE may consider theinformation in the two-stage grant triggered by the trigger that arrivesthe earliest to transmit a transport block in the scheduled subframe. Inan example, the UE may use the scheduling information in UL grantconsidered for the subframe (e.g., resource assignment, HARQ processnumber and redundancy version, MCS, Cyclic shift for DM RS and OCCindex, etc.) to create and attempt to transmit the transport block(s).In an example, the considered uplink grant may be multi-subframe grantand the UE may create and attempt to transmit multiple consecutivetransport blocks. In an example in FIG. 13, the wireless device receivesa one-stage grant DCI earlier than a trigger for two-stage grant DCI.The wireless device may use the information in the one-stage grant DCIto create and transmit the TB(s). In an example in FIG. 14, the wirelessdevice receives the trigger for a two-stage grant DCI earlier than theone-stage grant. The wireless device may use the information in thetwo-stage grant DCI to create and transmit the TB(s). In an example inFIG. 15, the wireless device receives the one-stage grant earlier thanthe trigger for the two-stage grant. The wireless device may use theinformation in the one-stage grant DCI to create and transmit the TB(s).In an example in FIG. 16, the wireless device receives two two-stagegrants and a single trigger. The wireless device may use the informationin the first (e.g., earlier received) two-stage grant to create andtransmit the TB(s). In an example in FIG. 17, the wireless device mayreceive two one-stage grants. The wireless device may use theinformation in the first (e.g., earlier received) one-stage grant tocreate and transmit the TB(s).

In an example embodiment, based on UE implementation, the UE may chooseto consider either the information in the first received grant or theinformation received in the last received grant to create and attempt totransmit transport block(s) on the scheduled subframe. In an example, ifone or more of the grants scheduling the UE for the subframe is (are)two-stage, based on the UE implementation, the UE may choose to considereither the subframe that the trigger for a two-stage grant is receivedor the subframe that the DCI for a two-stage grant is received forcomparison of arrival times of the grants. In an example, the UE may usethe scheduling information in UL grant considered for the subframe(e.g., resource assignment, HARQ process number and redundancy version,MCS, Cyclic shift for DM RS and OCC index, etc.) to create and attemptto transmit the transport block(s). In an example, the considered uplinkgrant may be multi-subframe grant and the UE may create and attempt totransmit multiple consecutive transport blocks.

In RAN WG1 Meeting #86 in August various agreements were made on twostage grant processing. For example, it was agreed that the timingbetween the 2nd trigger transmitted in subframe N and the earliest ULtransmission is a UE capability, if the earliest UL transmission isbefore subframe N+4 (UE capability signaling between transmission insubframe N+1 and N+2 and N+3).

3GPP documents R2-166717 and R2-166716 suggest that for two stepscheduling (using PUSCH trigger A (2StageGrant) and B (Trigger)), thereshould be UE capability signalling indicating the minimum time from thatstep 2 (Trigger) is received by the UE, until the UE performs thecorresponding uplink transmission. Also the two step schedulingframework is also not a mandatory UE capability and hence a capabilityindication is needed also for this. The document suggests adding a newfield to indicate whether the UE supports uplink scheduling using PUSCHtrigger A and PUSCH trigger B, and another new field to indicate theshortest time the UE supports to perform an uplink transmission afterhaving received PUSCH trigger B. Trigger A includes the grant, andtrigger B is a one bit trigger transmitted employing CC-RNTI. Theparameter earliestUL-AfterTriggerB is related to uplink scheduling usingPUSCH trigger A and PUSCH trigger B. This parameter indicates the timingbetween the PUSCH trigger B and the earliest time the UE supportsperforming the associated UL transmission. The parameters may beconfigured as ENUMERATED {nPlus1, nPlus2, nPlus3, nPlus4}. For receptionof PUSCH trigger B in subframe N, value nPlus1 indicates that the UEsupports performing the UL transmission in subframe N+1, value nPlus2indicates that the UE supports performing the UL transmission insubframe N+2, and so on. The parameter twoStepScheduling indicateswhether the UE supports uplink scheduling using PUSCH trigger A andPUSCH trigger B.

3GPP document R2-166425 adds a parameter earliestULTransmission-r14 inUE-EUTRA-Capability. The parameter arliestULTransmission is an integerfrom one to three [1 . . . 3] and indicates the minimum subframe offsetthat UE supports between the subframe where triggered grant is receivedand the subframe where the earliest UL transmission in two-stagescheduling can be sent on an LAA SCell. Absence of this field indicatesthe supported minimum subframe offset is 4 subframes.

The solutions presented above may be inefficient and may increase UEprocessing requirements. Example embodiments of the invention improvesthe current mechanisms for UE capability and capability signaling.Example embodiments may enable more efficient scheduling mechanisms. TheeNB may schedule transport blocks more efficiently for UEs when exampleembodiments are employed. Example embodiments increases uplink and/ordownlink throughput.

In an example embodiment, the timing between the first grant transmittedin subframe n and the earliest UL transmission may be a UE capability.The UE may start generating and processing one or more MAC PDUs when the2StageGrant is received. The UE may further process some of the MACand/or PHY processing after the trigger is received. Since theMAC-PDU/TB processing may start from the receipt of the first grant,transmission of the UE capability from the start of the first grant mayto be more beneficial than transmission of the UE capability about thetiming between the trigger transmitted in subframe N and the earliest ULtransmission. The UE capability about the timing between the triggertransmitted in subframe N and the earliest UL transmission from thetrigger may not be as useful to the eNB than the earliest ULtransmission from the 2StageGrant.

In an example scenario, a UE may be able to transmit in subframe m+4when a grant is received in subframe m. The UE may receive the2StageGrant in subframe m. The UE may receive the trigger in subframem+2, and the UE may be able to transmit the transport block in subframem+4. Or the UE may receive the trigger in subframe m+3 and the UE may beable to transmit the transport block in subframe m+4. The timing betweenthe trigger (in subframe N) and the transport block transmission (N+X+Y)is indicated in the first grant and the DCI comprising the trigger. Inthe example scenario, the timing between the trigger is one or twosubframes. The UE may need 3 to 4 subframes for MAC/PHY processing. Ifthe UE indicates in its capability that the earliest transmission is 4subframes after the trigger, this capability does not takes into accountthat the UE may start MAC processing after the 2StageGrant. If the UEindicates in its capability that the earliest transmission is forexample 2 or 1 subframes after the trigger, this capability does nottake into account that the UE may receive the trigger, for example, inthe subframe after the grant. In such a scenario, the UE may not haveenough time to perform MAC/PHY processing. In another scenario, the UEmay receive the grant in subframe N-10 and the trigger in subframe N,and may be able to perform PHY transmission in the subframe next to thetrigger (subframe N+1).

Example embodiment improves the capability signaling and eNB scheduling.The UE may transmit a UE capability message to a UE. The UE capabilitymessage may comprise a parameter indicating minimum time from that2StageGrant is received by the UE, until the UE performs thecorresponding uplink transmission. The eNB may employ this informationfor scheduling uplink TBs for the UE. FIG. 18. shows an exampleembodiment. The UE may transmit the minimum number for parameter k, thatit can handle, for example, k=3. In an example, the eNB may employ thisinformation to schedule TBs for uplink scheduling. Different UEs mayhave different capabilities regarding to this time interval k. Exampleembodiment, may also be applicable to one stage grant (normal grantswhere there is no trigger). In the example, the UE capability messagemay comprise a parameter indicating minimum time from a grant(2StageGrant or one stage uplink grant) is received by the UE, until theUE performs the corresponding uplink transmission.

In an example embodiment, there may be a UE capability signallingindicating the minimum time from the 2StageGrant is received by the UE,until the UE performs the corresponding uplink transmission. In anexample, the two step scheduling framework may not be a mandatory UEcapability and hence a capability indication may be needed for this. Inan example, the UE capability message may comprise a field to indicatewhether the UE supports uplink scheduling using PUSCH 2StageGrant andPUSCH Trigger, and a second field to indicate the shortest time the UEsupports to perform an uplink transmission after having received a2StageGrant. The grant may be an uplink Grant, and trigger may be a onebit trigger transmitted employing CC-RNTI. In an example, the parameterearliestUL-AfterGrant may be related to uplink scheduling using2StageGrant. In an example, the parameter earliestUL-AfterGrant may beapplicable to both 2StageGrant and 1Stage (normal) grant. This parametermay indicates the timing (number of subframes) between the PUSCH Grantand the earliest time the UE supports performing the associated ULtransmission. In an example, the parameters may be configured asENUMERATED {1, 2, 3, or 4}. For reception of PUSCH Grant in subframe N,value 1 indicates that the UE supports performing the UL transmission insubframe N+1, value 2 indicates that the UE supports performing the ULtransmission in subframe N+2, and so on. In an example, the parametersmay be configured as ENUMERATED {1, 2, 3}. In an example, when theparameter is not present it may imply that the parameter value is 4. Inan example, when the parameter is not present it may imply that2StageGrant may not be supported. In an example, the UE capabilitymessage may comprise a second parameter indicating whether the UEsupports uplink scheduling using 2StageGrant.

In an example embodiment, there may be a UE capability signallingindicating the minimum time from that 2StageGrant/Grant is received bythe UE, until the UE performs the corresponding uplink transmission. Inan example, the two step scheduling framework may be a mandatory UEcapability for UEs supporting configuration of uplink LAA and hence acapability indication may not be needed for indicating a 2StageGrantprocessing capability. In an example, the UE capability message maycomprise a second field/parameter to indicate the shortest time the UEsupports to perform an uplink transmission after having received thegrant. The grant may be an uplink grant, and trigger may be a one bittrigger transmitted employing CC-RNTI. In an example, the parameterearliestUL-AfterGrant may be related to uplink scheduling using2StageGrant. In an example, the parameter earliestUL-AfterGrant may beapplicable to both 2StageGrant and 1Stage (normal) grant. This parametermay indicates the timing (number of subframes) between the PUSCH Grantand the earliest time the UE supports performing the associated ULtransmission. In an example, the parameters may be configured asENUMERATED {1, 2, 3, or 4}. For reception of PUSCH Grant in subframe N,value 1 indicates that the UE supports performing the UL transmission insubframe N+1, value 2 indicates that the UE supports performing the ULtransmission in subframe N+2, and so on. In an example, the parametersmay be configured as ENUMERATED {1, 2, 3}. In an example, when theparameter is not present it may imply that the parameter value is 4.

The eNB may transmit a DCI comprising an uplink grant. The DCI may betransmitted in a (e)PDCCH UE specific search area corresponding toC-RNTI of the UE. The DCI may comprise resource allocation field, MCS,power control command, HARQ information, MIMO, and/or other parameters.The DCI may be transmitted on another cell (e.g. a licensed cell) usingcross carrier scheduling and may include a carrier indicator field. TheUE may monitor DCI corresponding to the CC-RNTI on the LAA cell. Whenthe trigger is received in subframe n, the UE may transmit one or moreTBs according to the DCI in subframe N+X+Y.

In an example embodiment, the 4 bit field ‘SF timing’ in DCI format0A/4A/0B/4B for the triggered grant may be reused as follows: When theUE may transmit after reception of the trigger is signaled to the UE. 2bits are reused to indicate X. When a UE receives a trigger in subframeN, the UE may be allowed to start transmission in subframe N+X+Y. X={0,1, 2, 3} indicated reusing two bits in the DCI. Y may be given by the ULburst offset in the C-PDCCH (common search space) DCI scrambled byCC-RNTI (e.g. in the same subframe where the trigger is transmitted).The UE may receive signaling in the first DCI 0A/4A/0B/4B grantindicating the number of subframes after which the grant becomes invalidreusing 2 bits. The initial grant becomes invalid if M ms after theinitial grant, no valid trigger has been received. 2 bit: M={8, 12, 16,20}. UE follows the LBT type indicated by the UL grant.

According to various embodiments, a device (such as, for example, awireless device, off-network wireless device, a base station, and/or thelike), may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 19 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. A wireless device may receive one or moremessages at 1910. The one or more messages may comprise configurationparameters for a cell. At 1920, a first downlink control information(DCI) may be received in a first transmission time interval (TTI). Thefirst DCI may comprise: a first field indicating a first resource blockassignment; and a first trigger field indicating whether the first DCIis a first triggered DCI. At 1930, a second DCI may be received in asecond TTI. The second DCI may comprise: a second field indicating asecond resource block assignment; and a second trigger field indicatingwhether the second DCI is a second triggered DCI. At 1940, a third DCImay be received in a third TTI and via a common control channel of thecell. The third DCI may comprise a third trigger field indicating atrigger. At 1950, the wireless device may select, as a selected DCI, oneof the first DCI or the second DCI at least based on a relative starttime of the first TTI and the second TTI. At 1960, at least onetransport block employing the selected DCI may be transmitted, inresponse to the trigger.

According to an embodiment, the cell may operate according to a framestructure type 3. According to an embodiment, the first DCI may be thefirst triggered DCI. According to an embodiment, the second DCI may bethe second triggered DCI. According to an embodiment, the one of thefirst DCI or the second DCI may be the first DCI in response to thetiming of the first TTI being earlier than the timing of the second TTI,otherwise the one of the first DCI or the second DCI may be the secondDCI. According to an embodiment, the first DCI may comprise a firsttiming offset field indicating a first transmission timing offset.According to an embodiment, the second DCI may comprise a second timingoffset field indicating a second transmission timing offset.

FIG. 20 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. A wireless device may receive one or moremessages at 2010. The one or more messages may comprise configurationparameters for a cell. At 2020, a first downlink control information(DCI) may be received in a first transmission time interval (TTI). Thefirst DCI may comprise: a first field indicating a first resource blockassignment; and a first trigger field indicating whether the first DCIis a first triggered DCI. At 2030, a second DCI may be received in asecond TTI. The second DCI may comprise: a second field indicating asecond resource block assignment; and a second trigger field indicatingwhether the second DCI is a second triggered DCI. At 2040, a third DCImay be received in a third TTI and via a common control channel of thecell. The third DCI may comprise a field indicating a trigger. At 2050,the wireless device may transmit, in response to the trigger, at leastone transport block employing one of the first DCI or the second DCIthat is selected at least based on a timing of the first TTI or thesecond TTI.

According to an embodiment, the cell may operate according to a framestructure type 3. According to an embodiment, the first DCI may be thefirst triggered DCI. According to an embodiment, the second DCI may bethe second triggered DCI. According to an embodiment, the one of thefirst DCI or the second DCI may be the first DCI in response to thetiming of the first TTI being earlier than the timing of the second TTI,otherwise the one of the first DCI or the second DCI may be the secondDCI. According to an embodiment, the first DCI may comprise a firsttiming offset field indicating a first transmission timing offset.According to an embodiment, the second DCI may comprise a second timingoffset field indicating a second transmission timing offset.

FIG. 21 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. A base station may transmit one or more messagesat 2110. The one or more messages may comprise configuration parametersfor a cell. At 2120, a first downlink control information (DCI) may betransmitted in a first transmission time interval (TTI). The first DCImay comprise: a first field indicating a first resource blockassignment; and a first trigger field indicating whether the first DCIis a first triggered DCI. At 2130, a second DCI may be transmitted in asecond TTI. The second DCI may comprise: a second field indicating asecond resource block assignment; and a second trigger field indicatingwhether the second DCI is a second triggered DCI. At 2140, a third TTImay be transmitted via a common control channel of the cell. The thirdDCI may comprise a field indicating a trigger. At 2150, the base stationmay receive, in response to the trigger, at least one transport blockemploying one of the first DCI or the second DCI that is selected atleast based on a timing of the first TTI or the second TTI.

According to an embodiment, the cell may operate according to a framestructure type 3. According to an embodiment, the first DCI may be thefirst triggered DCI. According to an embodiment, the second DCI may bethe second triggered DCI. According to an embodiment, the one of thefirst DCI or the second DCI may be the first DCI in response to thetiming of the first TTI being earlier than the timing of the second TTI,otherwise the one of the first DCI or the second DCI may be the secondDCI. According to an embodiment, the first DCI may comprise a firsttiming offset field indicating a first transmission timing offset.According to an embodiment, the second DCI may comprise a second timingoffset field indicating a second transmission timing offset.

FIG. 22 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2210, a wireless device may receive one ormore messages comprising configuration parameters for a cell. A firstdownlink control information (DCI) may be received at 2220. The firstDCI may comprise first transmission parameters for uplink transmissionsvia the cell. At 2230, a second DCI may be received. The second DCI maycomprise second transmission parameters for uplink transmissions via thecell. A trigger, corresponding to at least one of the first DCI or thesecond DCI, may be received at 2240. At 2250, the wireless device maytransmit, in response to the first DCI and the second DCI indicatingtransmission in a first/same subframe, one or more transport blocksemploying one of the first DCI or the second DCI at least based on afirst timing of the first DCI and a second timing of the second DCI.

FIG. 23 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2310, a wireless device may receive one ormore messages comprising configuration parameters for a cell. A firstdownlink control information (DCI) may be received at 2320. The firstDCI may comprise first transmission parameters for uplink transmissionsvia the cell. At 2330, a second DCI may be received. The second DCI maycomprise second transmission parameters for uplink transmissions via thecell. A trigger, corresponding to at least one of the first DCI or thesecond DCI, may be received at 2340. At 2350, the wireless device maytransmit, in response to the first DCI and the second DCI indicatingtransmission in a first/same subframe, one or more transport blocksemploying one of the first DCI or the second DCI at least based on atiming the trigger.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using LAA communication systems. However, one skilled in the art willrecognize that embodiments of the disclosure may also be implemented ina system comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 1). The disclosed methods and systems may be implementedin wireless or wireline systems. The features of various embodimentspresented in this disclosure may be combined. One or many features(method or system) of one embodiment may be implemented in otherembodiments. Only a limited number of example combinations are shown toindicate to one skilled in the art the possibility of features that maybe combined in various embodiments to create enhanced transmission andreception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

1. A method comprising: receiving, by a wireless device, one or moremessages comprising configuration parameters for a cell; receiving, in afirst transmission time interval (TTI), a first downlink controlinformation (DCI) comprising: a first field indicating a first resourceblock assignment; and a first trigger field indicating whether the firstDCI is a first triggered DCI; receiving, in a second TTI, a second DCIcomprising: a second field indicating a second resource blockassignment; and a second trigger field indicating whether the second DCIis a second triggered DCI; receiving, in a third TTI and via a commoncontrol channel of the cell, a third DCI comprising a third triggerfield indicating a trigger; selecting, as a selected DCI, one of thefirst DCI or the second DCI at least based on a relative start time ofthe first TTI and the second TTI; and transmitting, in response to thetrigger, at least one transport block employing the selected DCI.
 2. Themethod of claim 0, wherein the cell operates according to a framestructure type
 3. 3. The method of claim 0, wherein the first DCI is thefirst triggered DCI.
 4. The method of claim 0, wherein the second DCI isthe second triggered DCI.
 5. The method of claim 0, wherein the one ofthe first DCI or the second DCI is the first DCI in response to thetiming of the first TTI being earlier than the timing of the second TTI,otherwise the one of the first DCI or the second DCI is the second DCI.6. The method of claim 0, wherein the first DCI comprises a first timingoffset field indicating a first transmission timing offset.
 7. Themethod of claim 0, wherein the second DCI comprises a second timingoffset field indicating a second transmission timing offset.
 8. Awireless device comprising: one or more processors; memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: receive one or more messages comprisingconfiguration parameters for a cell; receive, in a first transmissiontime interval (TTI), a first downlink control information (DCI)comprising: a first field indicating a first resource block assignment;and a first trigger field indicating whether the first DCI is a firsttriggered DCI; receive, in a second TTI, a second DCI comprising: asecond field indicating a second resource block assignment; and a secondtrigger field indicating whether the second DCI is a second triggeredDCI; receive, in a third TTI and via a common control channel of thecell, a third DCI comprising a field indicating a trigger; and transmit,in response to the trigger, at least one transport block employing oneof the first DCI or the second DCI that is selected at least based on atiming of the first TTI or the second TTI.
 9. The wireless device ofclaim 0, wherein the cell operates according to a frame structure type3.
 10. The wireless device of claim 0, wherein the first DCI is thefirst triggered DCI.
 11. The wireless device of claim 0, wherein thesecond DCI is the second triggered DCI.
 12. The wireless device of claim0, wherein the one of the first DCI or the second DCI is the first DCIin response to the timing of the first TTI being earlier than the timingof the second TTI, otherwise the one of the first DCI or the second DCIis the second DCI.
 13. The wireless device of claim 0, wherein the firstDCI comprises a first timing offset field indicating a firsttransmission timing offset.
 14. The wireless device of claim 0, whereinthe second DCI comprises a second timing offset field indicating asecond transmission timing offset.
 15. A method comprising:transmitting, by a base station, one or more messages comprisingconfiguration parameters for a cell; transmitting, in a firsttransmission time interval (TTI), a first downlink control information(DCI) comprising: a first field indicating a first resource blockassignment; and a first trigger field indicating whether the first DCIis a first triggered DCI; transmitting, in a second TTI, a second DCIcomprising: a second field indicating a second resource blockassignment; and a second trigger field indicating whether the second DCIis a second triggered DCI; transmitting, in a third TTI and via a commoncontrol channel of the cell, a third DCI comprising a field indicating atrigger; and receiving, by the base station, in response to the trigger,at least one transport block employing one of the first DCI or thesecond DCI that is selected at least based on a timing of the first TTIor the second TTI.
 16. The method of claim 15, wherein the cell operatesaccording to a frame structure type
 3. 17. The method of claim 15,wherein the first DCI is the first triggered DCI.
 18. The method ofclaim 15, wherein the second DCI is the second triggered DCI.
 19. Themethod of claim 15, wherein the one of the first DCI or the second DCIis the first DCI in response to the timing of the first TTI beingearlier than the timing of the second TTI, otherwise the one of thefirst DCI or the second DCI is the second DCI.
 20. The method of claim15, wherein the first DCI comprises a first timing offset fieldindicating a first transmission timing offset.